Systems and methods of pending transaction augmentation and automatic attachment to settled transactions

ABSTRACT

A method including: receiving an indication of a transaction authorization of a pending transaction, the transaction authorization being requested using a financial account associated with a user; outputting for transmission, to a user device associated with the user, a request for purchase information corresponding to the pending transaction; receiving, from the user device, receipt image data corresponding to a receipt related the pending transaction; storing data indicative of the receipt in correspondence with the pending transaction; determining, based on analyzing a plurality of posted transactions of the financial account, a first posted transaction corresponding to the pending transaction; and storing the data indicative of the receipt in correspondence with the first posted transaction.

FIELD

The disclosed technology generally relates to transaction processing,and, more particularly, systems and methods for appending data topending transactions and attaching to corresponding posted transaction.

BACKGROUND

Many organizations monitor and track employee expenses. Organizationoften require documentation to approve or reimburse expenses. Yet, inthe related art, employees are unable to electronically appendinformation to transactions when they occur. For example, if an employeepays for a business meal, the company may require a receipt and a listof attending individuals in order to reimburse or properly credit theexpense. However, in related art solutions, employees must maintaintheir receipts and remember dates, attendees, and expense purposes daysor weeks after the expense in incurred. This creates a highly errorprone process, in terms of lost receipts and fading memories.

For instance, when a credit card is used to conduct a transaction, atemporary pending transaction is placed on the credit card. Pendingtransactions may generally be considered real-time checks to ensure thata specific financial account is able to process the proposedtransaction. This temporary transaction is released after a few days,but is not connected with a posted (e.g., settled) transaction placed onthe credit card, and identifying pairs of pending and postedtransactions is non-trivial. For example, pending and postedtransactions may have different transaction values (e.g., tips), apending transaction may simply be a check on validity (e.g., and notdirectly leading to a posted transaction), multiple processing attemptsmay result in a plurality of pending transactions but a single posedtransaction, and an authorization amount or date may change betweenpending and posted transactions (e.g., for a multi-day rental).Furthermore, posted transactions are not always in a same order as thecorresponding pending transactions. Thus, related art solutions eitherrequire delaying appending of receipts and information until after atransaction settles (often days or weeks after the transaction date), oronly capturing receipts in real-time and utilizing optical characterrecognition (OCR) to attempt to match receipts to ultimately settledtransactions. However, OCR is unreliable in this space (failing morethan 15% of the time) due to a variety of factors, such as difficulty indeciphering handwriting, old and/or degrading paper and ink (e.g.,receipt paper), and idiosyncratic formatting, and such solutions do notallow appending additional information often required for expensereports (e.g., names, department and/or client IDs, descriptions).

Faulty employee memories and the unreliability of prior art systems cangreatly increase overhead costs. For example, if an employeemisremembers or mis-inputs a date or misapplies a charge, billingprocesses may be disrupted, requiring investigations,issuance/reissuance of bills and payments, and disruptions to bothemployees and administrators. Furthermore, denial of reimbursementrequests whether accurately (e.g., because and employee is mistakenabout reimbursement policies) or inaccurately (e.g., due to a lack ofdocumentation or failure to meet some other formality) can havedetrimental effects on employee morale. Thus, the shortcomings of therelated art systems can have compounding effects that are detrimental toorganizations.

Therefore, there is a need for improved systems and methods to providetransaction augmentation in real-time at the time of sale. Certainaspects of the present disclosure attempt to address these and otherissues.

BRIEF SUMMARY

Disclosed embodiments provide systems and methods for pendingtransaction augmentation and/or automatic attachment to settledtransactions.

According to some embodiments, there is provided a method including:receiving an indication of a transaction authorization of a pendingtransaction, the transaction authorization being requested using afinancial account associated with a user; outputting for transmission,to a user device associated with the user, a request for purchaseinformation corresponding to the pending transaction; receiving, fromthe user device, receipt image data corresponding to a receipt relatedthe pending transaction; storing data indicative of the receipt incorrespondence with the pending transaction; determining, based onanalyzing a plurality of posted transactions of the financial account, afirst posted transaction corresponding to the pending transaction; andstoring the data indicative of the receipt in correspondence with thefirst posted transaction.

The method may further include: receiving, with the receipt image data,transaction classification information; storing the transactionclassification information in correspondence with the pendingtransaction; and storing the transaction classification information incorrespondence with the first posted transaction.

The method may further include: analyzing the receipt image data usingoptical character recognition; and extracting receipt information fromthe analyzed receipt image data as the data indicative of the receiptimage.

The pending transaction may have a first transaction value, and thefirst posted transaction has a second, different transaction value.

Determining the first posted transaction may include: analyzing thereceipt image data to identify one or more post-authorizationline-items, adjusting the first transaction value in accordance with theidentified one or more post-authorization line items, and determiningthe first posted transaction based at least in part on the adjustedfirst transaction value.

The request for purchase information corresponding to the pendingtransaction may be configured to trigger a persistent request for thereceipt image data.

According to some embodiments, there is provided a user deviceincluding: at least one processor; and at least one memory having storedthereon computer program code that, when executed by the at least oneprocessor, controls the user device to: activate, on the user device, avirtual wallet application, the virtual wallet application including oneor more virtual transaction cards; responsive to a first virtualtransaction card of the one or more virtual transaction cards beingutilized in an approved transaction, output for display, on the userdevice, a prompt to provide purchase information; receive receipt datacorresponding to a receipt related the approved transaction; and outputfor transmission, to a transaction server, the receipt data inassociation with the approved transaction.

The user device may further include a camera. Receiving the receipt datacorresponding to the receipt may include: activating, on the userdevice, a camera application corresponding to the camera; and capturing,using the camera and the camera application, an image of the receipt.

The computer program code, when executed by the at least one processor,may further control the user device to verify the image corresponds tothe receipt.

Verifying the image may correspond to the receipt includes: analyzingthe image using one or more optical-character recognition algorithms;and comparing the analyzed image with transaction information of theapproved transaction.

Receiving the receipt data may correspond to the receipt includes:activating, on the user device, an email application; identifying,within the email application, a receipt email from among a plurality ofemails; and extracting receipt information from the identified receiptemail.

Identifying the receipt email may include identifying the receipt emailbased on at least one from among respective delivery dates of theplurality of emails, respective sender addresses of the plurality ofemails, and text-analysis of one or more of the plurality of emails.

Extracting the receipt information may include capturing a screenshot ofthe identified receipt email.

Extracting the receipt information may include forwarding the identifiedreceipt email to an address associated with the transaction server.

Forwarding the identified receipt email may include: receiving anindication of a user input of additional transaction information, theadditional transaction information including one or more of notes, alist of attendees, and project codes; and forwarding the additionaltransaction information together with the identified receipt email tothe address associated with the transaction server.

The computer program code, when executed by the at least one processor,may further control the user device to: execute, on the user device, areceipt capturing application; receive the receipt data within thereceipt capturing application; and provide, within the receipt capturingapplication, at least one from among: a notes field for receivingcontext to an authorized transaction, an attendees field for receiving alisting one or more attendees associated with the authorizedtransaction, and a project field for receiving relevant project codesassociated with the authorized transaction.

The computer program code, when executed by the at least one processor,may further control the user device to automatically populate theattendees field based on a list of attendees of an event associated withthe authorized transaction.

The user device may further include a camera. The computer program code,when executed by the at least one processor, may further control theuser device to: activate, on the user device, a camera applicationcorresponding to the camera; capture, using the camera and the cameraapplication, one or more images of one or more purchased itemsassociated with the authorized transaction; identify, based on the oneor more images, one or more item identities corresponding one or morepurchased items; and output for transmission, to the transaction server,data indicative of a list of the one or more items in association withthe approved transaction.

The camera application may include a barcode reader, and identifying theone or more items includes identifying, within the one or more images,one or more barcodes corresponding to the one or more items;transforming the one or more barcodes into one or more numericalrepresentations; and matching the one or more numerical representationsto identities of the one or more items.

According to some embodiments, there is provided a system including: atleast one processor; and at least one memory having stored thereoncomputer program code that, when executed by the at least one processor,controls the system to: receive, from a user device, an indication of apending transaction conducted using a virtual transaction cardassociated with a financial account maintained by a financialinstitution, the virtual transaction card being instantiated on the userdevice; outputting for transmission, to the user device, a request forpurchase information corresponding to the pending transaction;receiving, from the user device, receipt image data corresponding to areceipt related the pending transaction; storing data indicative of thereceipt in correspondence with the pending transaction; determining,based on analyzing a plurality of posted transactions of the financialaccount, a first posted transaction corresponding to the pendingtransaction; and storing the data indicative of the receipt incorrespondence with the first posted transaction.

Other implementations, features, and aspects of the disclosed technologyare described in detail herein and are considered a part of the claimeddisclosed technology. Other implementations, features, and aspects canbe understood with reference to the following detailed description,accompanying drawings, and claims.

BRIEF DESCRIPTION OF THE FIGURES

Reference will now be made to the accompanying figures and flowdiagrams, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a diagram of an example system environment that may be used toimplement one or more embodiments of the present disclosure;

FIG. 2 is a component diagram of a transaction management serveraccording to an example embodiment;

FIGS. 3 and 4 are flowcharts of one or more methods according to certainexample embodiments.

DETAILED DESCRIPTION

Some implementations of the disclosed technology will be described morefully with reference to the accompanying drawings. This disclosedtechnology may, however, be embodied in many different forms and shouldnot be construed as limited to the implementations set forth herein. Thecomponents described hereinafter as making up various elements of thedisclosed technology are intended to be illustrative and notrestrictive. Many suitable components that would perform the same orsimilar functions as components described herein are intended to beembraced within the scope of the disclosed electronic devices andmethods. Such other components not described herein may include, but arenot limited to, for example, components developed after development ofthe disclosed technology.

It is also to be understood that the mention of one or more method stepsdoes not preclude the presence of additional method steps or interveningmethod steps between those steps expressly identified. Similarly, it isalso to be understood that the mention of one or more components in adevice or system does not preclude the presence of additional componentsor intervening components between those components expressly identified.

According to some embodiments, there is provided systems and methods forincluding attachments to pending transactions and resolving the pendingtransactions to executed transactions. For example, in some cases, asystem identifies an incoming pending transaction and sends a userdevice a request for information corresponding to the transaction. Theuser device may belong to a person associated with an account used forthe transaction. The user device sends a receipt image, which the systemstores with the pending transaction. Later, the system analyzes postedtransactions to identify one that corresponds to the pendingtransaction, and then stores the receipt in association with theidentified posted transaction. The receipt image may include one or moreof a transaction classification and a post-authorization line-item. Thepending and posted transactions may have different values. In somecases, the system determines the first posted transaction, at least inpart, by analyzing the receipt image to identify a post-authorizationline-item (e.g., tax or tip) and adjusting the pending transaction valueby the line-items. In some cases, request for purchase information maytrigger a persistent request for the receipt image data from the user(e.g., on one or more user devices).

In some embodiments a user device uses a virtual transaction card toperform a transaction. When the transaction is approved (i.e., as apending transaction), the user device prompts the user to providereceipt data. Once the receipt data is received, the user device postsit to a transaction server. User may input the receipt data by capturinga picture of the receipt with a camera of the user device. The userdevice may verify that the image includes the receipt data (e.g.,comparing information in the image to the pending transaction) beforeaccepting the image as transaction information (or purchaseinformation). In some cases, the receipt data may be extracted from areceipt email accessed via the user device (e.g., by taking a screenshotof a rendered email or automatically forwarding the email, such as to aone-time, transaction specific email account). The receipt email may beautomatically identified from within an email application, e.g., basedon at least one from among respective delivery dates of the plurality ofemails, respective sender addresses of the plurality of emails, andtext-analysis of one or more of the plurality of emails. In some cases,a user may input additional transaction information (e.g., notes,attendees' lists, project codes) into the user device and the receiptdata and additional transaction information may be delivered to thetransaction server together. The information may be input into anapplication executing on the user device. The attendees may be autopopulated based on a list of attendees of an event associated with thepending transaction (e.g., RSVP's to a lunch meeting). In some cases,the user device may identify and/or extract individual items from thereceipt data and associate the same with the pending transaction. Insome cases, the user device may receive barcodes (e.g., through imagecapture or a barcode scanner), identify the scanned items, and associatethem with the pending transaction.

In some cases, a system may receive, from a user device, an indicationof a pending transaction using a virtual transaction card on the userdevice, and output, to the user device, a request for purchaseinformation. The system may receive receipt image data and store thereceipt in association with the pending transaction. The system mayanalyze posted transactions to identify one that corresponds to thepending transaction, and then store the receipt data in correspondencewith the identified posted transaction.

Reference will now be made in detail to example embodiments of thedisclosed technology, examples of which are illustrated in theaccompanying drawings and disclosed herein. Wherever convenient, thesame references numbers will be used throughout the drawings to refer tothe same or like parts.

FIG. 1 is a diagram of an example system environment that may be used toimplement one or more embodiments of the present disclosure. Thecomponents and arrangements shown in FIG. 1 are not intended to limitthe disclosed embodiments as the components used to implement thedisclosed processes and features may vary.

In accordance with disclosed embodiments, system environment 100 mayinclude a transaction management server 110 in communication with a userdevice 120, a transaction server 130, and a merchant device 140 vianetwork 105. In some embodiments, transaction management server 110 mayalso be in communication with various databases (e.g., email databases).User device 120 may be a mobile computing device (e.g., a smart phone,tablet computer, smart wearable device, portable laptop computer, voicecommand device, wearable augmented reality device, or other mobilecomputing device). An example architecture that may be used to implementone or more of the transaction management server 110, user device 120,transaction server 130, and merchant device 140 is described below withreference to FIG. 2.

The transaction management server 110 may provide expense managementservices. For example, an institutional client card may desire to trackspending for employee credit card for tax and/or billing purposes.Transaction management server 110 may provide for appending purchasedocumentation and/or notes to pending transactions and transferring thesame to posted transactions. For example, one or more notes may bemanually entered by an employee to provide an explanation of transactiondetails or other relevant information that may not be apparent from thesubmitted documentation. In some cases, transaction management server110 communicates with transaction server 130, which may be associatedwith a financial institution and records financial transactions.Transaction management server 110 may receive transaction informationfor transactions (e.g., pending and posted) associated with a specificfinancial account from the transaction server 130. In some cases,transaction management server 110 may receive an indication of a pendingtransaction at a financial account (e.g., from transaction server 130 oruser device 120) and request, from the user device 120, purchaseinformation corresponding to the pending transaction. Once received,transaction management server 110 may associate the purchase informationwith the pending transaction. Later, transaction management server 110receives (e.g., from transaction server 130) indications of one or moreposted transactions on the financial account. Transaction managementserver 110 resolves the pending transaction to one or more of the postedtransaction and stores the purchase information in association with atleast one of the one or more posted transactions. For example,transaction management server 110 may identify the plurality oftransactions and request a manually intervention, may have a defaultassociation (e.g., attach to the most expensive transaction or amost-closely matching transaction), or determine that the plurality ofposted transactions correspond to the single pending transaction bycomparing respective transaction data (e.g., location, merchant, date,and costs). In some other cases, multiple pending transactions mayresolve into a single posted transaction, and a plurality of transactioninformation associated with the multiple pending transactions may bemerged (e.g., by transaction management server 110) and attached to theone posted transaction.

User device 120 may be associated with an individual who is authorizedto use a financial account (e.g., an account holder or authorized user).When a transaction is conducted (i.e., a pending transaction in added tothe financial account), transaction management server 110 may prompt theuser to provide transaction details via the user device 120. Forexample, transaction management server 110 may trigger an expensemanagement program to launch on the user device 120. The user may,through the user device 120, provide transaction information to thetransaction management server 110. As non-limiting examples, thetransaction information may include a receipt image (e.g., captured witha camera of the user device 120), attendees list, customer or projectnumbers, accounting (e.g., general ledger or GR) codes, departmentnumber, facility ID, department ID, location information, free-entry(e.g., character string), and/or customized fields.

In some cases, the user device 120 may implement a virtual wallet thatincludes a virtual transaction card linked to the financial account(e.g., at merchant device 140). When the virtual transaction card isused to make a purchase (e.g., through NFC payment communication withmerchant device 140), the user device 120 may automatically outputprompts to provide the transaction information (e.g., through an expensemanagement application). In some cases, the transaction information maybe provided through an email application (e.g., by capturing an image ofa receipt email and/or forwarding the receipt email). In some instances,the expense management application may automatically identify andcapture a receipt email in the user's email account that corresponds tothe pending transaction, for example, through an email plugin or as aforwarded email. In some cases, the receipt may be captured through atext message (either from the merchant or forwarded from the purchaser).In certain cases, an attendees list may be generated and attached froman event RSVP (e.g., from an event on a calendar stored on user device120). In some cases, the attendees in the attendee list may beselectable such that the user of user device 120 may alter the listbased on actual attendance. In certain implementations, the attendeelist may be selected based on a location of the user device 120 (e.g.,if the event location is at a hotel, the attendee list will only beattached if the user device 120 is determined to be at the hotel).

In some cases, the attendee list may be generated based on proximitysensors. For example, user device 120 may connect or identify nearbydevices and/or attendees associated with the nearby devices. The usermay then augment or alter the attendee list as necessary, such as byselecting/deselecting names and/or entering additional names. As anotherexample, an attendees list may be generated from an event RSVP, and theproximity sensors may cross-check the RSVP list with nearby devicesand/or attendees associated with the nearby devices. In some cases, userdevice 120 location data (e.g., from a GPS) may be used to automaticallyselect a client/job code (e.g., if the location data is inside aclient's office), or provide an expected expense type (e.g., businessmeal in a restaurant). In certain implementations, the user device 120location data (e.g., from a GPS) may be attached to a reimbursementrequest, for example, as confirmation of attendance to an event. Incertain embodiments, user device 120 may attach the transactioninformation to a transaction request (e.g., the additional informationis captured and provided to the merchant; the merchant sends thepurchase information with the transaction authorization request).

Transaction server 130 may be associated with a financial institution.For example, transaction server 130 may process financial transactions,or manage individual accounts. One of ordinary skill will recognize thattransaction server 130 may include one or more logically or physicallydistinct systems. In some cases, certain aspects of the transactionmanagement server 110 may be implemented through or with transactionserver 130 (e.g., if the financial institution provides transactionmanagement services).

Merchant device 140 may be, as a non-limiting example, a point-of-saledevice. Merchant device 140 may submit transaction authorization totransaction server 130, which, when authorized, become pendingtransactions. Merchant device 140 may also request payment fromtransaction server 130 (e.g., through the automated clearing house(ACH)), which then become posted transactions.

Network 105 may be of any suitable type, including individualconnections via the internet such as cellular or Wi-Fi networks. In someembodiments, network 105 may connect terminals using direct connectionssuch as radio-frequency identification (RFID), near-field communication(NFC), Bluetooth™, low-energy Bluetooth™ (BLE), Wi-Fi™, ZigBee™, ambientbackscatter communications (ABC) protocols, USB, or LAN. Because theinformation transmitted may be personal or confidential, securityconcerns may dictate one or more of these types of connections beencrypted or otherwise secured. In some embodiments, however, theinformation being transmitted may be less personal, and therefore thenetwork connections may be selected for convenience over security.

An example embodiment of transaction management server 110 is shown inmore detail in FIG. 2. User device 120, transaction server 130, and/ormerchant device 140 may have a similar structure and components that aresimilar to those described with respect to transaction management server110. As shown, transaction management server 110 may include a processor210, an input/output (“I/O”) device 220, a memory 230 containing anoperating system (“OS”) 240 and a program 250. For example, transactionmanagement server 110 may be a single server or may be configured as adistributed computer system including multiple servers or computers thatinteroperate to perform one or more of the processes and functionalitiesassociated with the disclosed embodiments. In some embodiments,transaction management server 110 may further include a peripheralinterface, a transceiver, a mobile network interface in communicationwith processor 210, a bus configured to facilitate communication betweenthe various components of the transaction management server 110, and apower source configured to power one or more components of transactionmanagement server 110.

A peripheral interface may include the hardware, firmware and/orsoftware that enables communication with various peripheral devices,such as media drives (e.g., magnetic disk, solid state, or optical diskdrives), other processing devices, or any other input source used inconnection with the instant techniques. In some embodiments, aperipheral interface may include a serial port, a parallel port, ageneral-purpose input and output (GPIO) port, a game port, a universalserial bus (USB), a micro-USB port, a high definition multimedia (HDMI)port, a video port, an audio port, a Bluetooth™ port, a near-fieldcommunication (NFC) port, another like communication interface, or anycombination thereof.

In some embodiments, a transceiver may be configured to communicate withcompatible devices and ID tags when they are within a predeterminedrange. A transceiver may be compatible with one or more of:radio-frequency identification (RFID), near-field communication (NFC),Bluetooth™, low-energy Bluetooth™ (BLE), Wi-Fi™, ZigBee™, ambientbackscatter communications (ABC) protocols or similar technologies.

A mobile network interface may provide access to a cellular network, theInternet, or another wide-area network. In some embodiments, a mobilenetwork interface may include hardware, firmware, and/or software thatallows processor(s) 210 to communicate with other devices via wired orwireless networks, whether local or wide area, private or public, asknown in the art. A power source may be configured to provide anappropriate alternating current (AC) or direct current (DC) to powercomponents.

As described above, transaction management server 110 may configured toremotely communicate with one or more other devices, such as user device120. According to some embodiments, transaction management server 110may utilize a dual-stage neural network pipeline to detect and recognizetextual information.

Processor 210 may include one or more of a microprocessor,microcontroller, digital signal processor, co-processor or the like orcombinations thereof capable of executing stored instructions andoperating upon stored data. Memory 230 may include, in someimplementations, one or more suitable types of memory (e.g. such asvolatile or non-volatile memory, random access memory (RAM), read onlymemory (ROM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), magnetic disks, optical disks,floppy disks, hard disks, removable cartridges, flash memory, aredundant array of independent disks (RAID), and the like), for storingfiles including an operating system, application programs (including,for example, a web browser application, a widget or gadget engine, andor other applications, as necessary), executable instructions and data.In one embodiment, the processing techniques described herein areimplemented as a combination of executable instructions and data withinthe memory 230.

Processor 210 may be one or more known processing devices, such as amicroprocessor from the Pentium™ family manufactured by Intel™ or theTurion™ family manufactured by AMD™. Processor 210 may constitute asingle core or multiple core processor that executes parallel processessimultaneously. For example, processor 210 may be a single coreprocessor that is configured with virtual processing technologies. Incertain embodiments, processor 210 may use logical processors tosimultaneously execute and control multiple processes. Processor 210 mayimplement virtual machine technologies, or other similar knowntechnologies to provide the ability to execute, control, run,manipulate, store, etc. multiple software processes, applications,programs, etc. One of ordinary skill in the art would understand thatother types of processor arrangements could be implemented that providefor the capabilities disclosed herein.

Transaction management server 110 may include one or more storagedevices configured to store information used by processor 210 (or othercomponents) to perform certain functions related to the disclosedembodiments. In one example, transaction management server 110 mayinclude memory 230 that includes instructions to enable processor 210 toexecute one or more applications, such as server applications, networkcommunication processes, and any other type of application or softwareknown to be available on computer systems. Alternatively, theinstructions, application programs, etc. may be stored in an externalstorage or available from a memory over a network. The one or morestorage devices may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible computer-readable medium.

In one embodiment, transaction management server 110 may include memory230 that includes instructions that, when executed by processor 210,perform one or more processes consistent with the functionalitiesdisclosed herein. Methods, systems, and articles of manufactureconsistent with disclosed embodiments are not limited to separateprograms or computers configured to perform dedicated tasks. Forexample, transaction management server 110 may include memory 230 thatmay include one or more programs 250 to perform one or more functions ofthe disclosed embodiments. Moreover, processor 210 may execute one ormore programs 250 located remotely from transaction management server110. For example, transaction management server 110 may access one ormore remote programs 250, that, when executed, perform functions relatedto disclosed embodiments.

Memory 230 may include one or more memory devices that store data andinstructions used to perform one or more features of the disclosedembodiments. Memory 230 may also include any combination of one or moredatabases controlled by memory controller devices (e.g., server(s),etc.) or software, such as document management systems, Microsoft™ SQLdatabases, SharePoint™ databases, Oracle™ databases, Sybase™ databases,or other relational databases. Memory 230 may include softwarecomponents that, when executed by processor 210, perform one or moreprocesses consistent with the disclosed embodiments. In someembodiments, memory 230 may include an image processing database 260 anda neural-network pipeline database 270 for storing related data toenable transaction management server 110 to perform one or more of theprocesses and functionalities associated with the disclosed embodiments.

Transaction management server 110 may also be communicatively connectedto one or more memory devices (e.g., databases (not shown)) locally orthrough a network. The remote memory devices may be configured to storeinformation and may be accessed and/or managed by transaction managementserver 110. By way of example, the remote memory devices may be documentmanagement systems, Microsoft™ SQL database, SharePoint™ databases,Oracle™ databases, Sybase™ databases, or other relational databases.Systems and methods consistent with disclosed embodiments, however, arenot limited to separate databases or even to the use of a database.

Transaction management server 110 may also include one or more I/Odevices 220 that may include one or more interfaces for receivingsignals or input from devices and providing signals or output to one ormore devices that allow data to be received and/or transmitted bytransaction management server 110. For example, transaction managementserver 110 may include interface components, which may provideinterfaces to one or more input devices, such as one or more keyboards,mouse devices, touch screens, track pads, trackballs, scroll wheels,digital cameras, microphones, sensors, and the like, that enabletransaction management server 110 to receive data from one or more users(such as via user device 120).

In example embodiments of the disclosed technology, transactionmanagement server 110 may include any number of hardware and/or softwareapplications that are executed to facilitate any of the operations. Theone or more I/O interfaces may be utilized to receive or collect dataand/or user instructions from a wide variety of input devices. Receiveddata may be processed by one or more computer processors as desired invarious implementations of the disclosed technology and/or stored in oneor more memory devices.

While transaction management server 110 has been described as one formfor implementing the techniques described herein, those having ordinaryskill in the art will appreciate that other, functionally equivalenttechniques may be employed. For example, as known in the art, some orall of the functionality implemented via executable instructions mayalso be implemented using firmware and/or hardware devices such asapplication specific integrated circuits (ASICs), programmable logicarrays, state machines, etc. Furthermore, other implementations of thetransaction management server 110 may include a greater or lesser numberof components than those illustrated.

FIG. 3 shows a flowchart of a method 300 according to an exampleembodiment. Method 300 may be performed by, for example, transactionmanagement server 110.

Transaction management server 110 receives 310 an indication of atransaction authorization of a pending transaction. The transaction maybe requested using a financial account associated with a user (e.g., ofuser device 120). In some cases, the indication of a pending transactionmay be received from a financial institution system (e.g., transactionserver 130). In other instances, the indication of the pendingtransaction may be received from a user device (e.g., user device 120).For instance, use of a virtual card instantiated on user device 120 maytrigger user device 120 to notify transaction management server 110 ofthe pending transaction. In some cases, transaction management server110 may poll transaction server 130 for the pending transactioninformation after being notified by user device 120.

Transaction management server 110 outputs 320 (e.g., outputs fortransmission), a request for purchase information corresponding to thepending transaction. For example, transaction management server 110 mayrequest that user device 120 provide additional information regardingthe pending transaction. In some cases, transaction management server110 may trigger user device 120 to launch an expense managementapplication for capturing/receiving transaction information. In somecases, requesting the purchase information from user device 120 maycreate a persistent request. For example, a user may be prevented fromaccessing one or more features of the user device 120 until the purchaseinformation is provided. In some cases, the request for transactioninformation may be repeatedly transmitted to one or more user devices120 (e.g., computer, phone, laptop) until the purchase information isprovided.

Next, transaction management server 110 receives 330 the purchaseinformation (e.g., from user device 120). Transaction management server110 stores 340 the purchase information with the pending transaction.For example, transaction management server 110 may keep a copy ofrecords of pending and posted transactions and link the purchaseinformation to the pending transaction. As non-limiting examples, thepurchase information may include receipt image data, attendees list,client and/or project codes, location information, transactionclassification information, and/or event information. In a case wherethe purchase information includes receipt image data, transactionmanagement server 110 may analyze the receipt image data (e.g., usingoptical character recognition) to extract receipt information (e.g.,merchants, time codes, items, costs), and store the extracted receiptinformation with the pending transaction. Transaction management server110 may confirm that the receipt image corresponds to the pendingtransaction, such as by analyzing the image using OCR algorithm(s) andcomparing the captured text data (e.g., dates, merchants, locations,cost) to the pending transaction (e.g., transaction date, location,amount).

Transaction management server 110 analyzes 350 one or more postedtransactions and matches a first posted transaction to the pendingtransaction. The transaction management server 110 may receive theposted transactions from transaction server 130 (e.g., through daily orhourly polling). In some cases, the pending transaction andcorresponding posted transaction have different transaction values.Thus, to match the transactions, transaction management server 110 mayidentify, within receipt image data, one or more post-authorization lineitems (e.g., tip on a restaurant bill) and adjust the transaction valueof the pending transaction by the post-authorization amount to helpidentify a corresponding posted transaction. The identification ofpost-authorization line items may be performed using machine-learningalgorithms, though this is only an example.

In some cases, the notes entered for the pending transaction may be usedto direct the reconciliation of posted transactions with pendingtransactions. For example, the notes may include indications of avendor, and transaction management server 110 may use natural languageprocessing to determine the vendor for the pending transaction from thenotes and to better associate the pending transaction with a postedtransaction. In some cases, the notes may not relate to transactionreconciliation, but rather be attached for accounting or reportingpurposes (e.g., to be reviewed by the accounting department shouldfurther review be required).

As will be understood by one of ordinary skill in light of the presentdisclosure, typically pending transactions and posted transactions havegreat overlap. However, exceptions to this general rule (e.g., differenttransaction amounts, pending transactions without posted transactions,multiple pending transactions resolved to a single posted transaction, asingle pending transaction resolving to a plurality of postedtransactions, and/or changes to transaction dates, amounts, orlocations) are very difficult to identify using related-art techniques.Accordingly, in some cases, machine-learning is used to analyze theposted and pending transactions and purchase information to identifymatches. For example, by training machine learning algorithms, theyalgorithms may decide whether to match or not match. Exampledetermination characteristics include vendor name, date and times,transaction amount, and transaction location. The machine learning maybe updated during execution, for example, by prompting users and/orspot-checking assignments. In some cases, past decisions may be storedin a database and used for training the machine learning algorithms.

Transaction management server 110 then stores the purchases informationwith the matched posted transaction. In some cases, storing the purchaseinformation may include providing the purchase information totransaction server 130 as a tag with the processed transaction. In someimplementations, transaction management server 110 may create an expensereport, for example, by embedding the purchase information and postedtransaction details into a report and sending the same to anorganization's accounting department.

FIG. 4 shows a flowchart of a method 400 according to an exampleembodiment. Method 400 may be performed by, for example, user device120.

User device 120 activates 410 (e.g., in response to user commands) avirtual wallet application. The virtual wallet includes one or morevirtual transaction cards. The virtual transaction cards may beassociated with a financial account handled by transaction server 130.Once a virtual transaction card is used to make a purchase, user device120 may prompt 420 the user for purchase information. For example, userdevice 120 may output a popup on a display of the user device 120requesting the purchase information. In some cases, user device 120 mayexecute and/or activate an expense management application, e.g.,implementing one or more graphical-user interfaces (GUIs). For example,the expense management application may include fields for notes,receipts, expense report kind, expense category or type, designation ofexpense (personal or business), attendees, etc. These may be editable astext fields, drop-down menus, check boxes, and the like. The user mayenter the information through the user device 120 (e.g., into theexpense management application).

User device 120 receives 430 receipt data. The receipt data may include,receipt data and/or configurable data (e.g., notes, attendees, items,project/department/client codes). In some cases, the user device 120 maycapture an image of a printed receipt. User device 120 may be configuredto analyze (e.g., with OCR, edge detection, and/or image analysis) theimage to confirm that received image includes a receipt. Confirming theimage includes a receipt may include analyzing the image using OCRalgorithm(s) and comparing the captured text data (e.g., dates,merchants, locations, cost, notes) to transaction information capturedfrom the virtual transaction card to confirm that the receipt in theimage corresponds to the transaction.

In some cases, user device 120 may receive the receipt data through anemail application. For example, user device 120 may activate an emailapplication, identify within the email application a receipt email, andextract the receipt information. In some cases, a user may identify thereceipt information. In other implementation, the user device 120 mayidentify the receipt email based on at least one sending/receivingtimestamps on the emails, sender addresses, and text and/orimage-analysis of the plurality of emails. For example, user device 120a receipt email as one sent subsequent (but near-in time) to the use ofthe virtual transaction card, may be from a domain associated with themerchant, and/or include certain receipt identifiers, such as “total,”“tax,” and “order number.” In certain instances, merchants and/orvendors may forward email receipt associated with registered users to acentral receipt processing center (e.g., forward the receipt email to adesignated email address), along with purchaser identification. In somecases, user device 120 may extract the receipt information by capturinga screenshot (or image rendering) of the receipt email. In some cases,user device 120 may forward the receipt email to an address associatedwith transaction management server 110. The forwarded email may includeadditional information (e.g., notes, a list of attendees, and projectcodes).

In some cases, the configurable data may be received through userinterfaces (UI) (e.g., graphical user interfaces (GUI)) of an expensemanagement application. The expense management application may includeone or more fields including a notes field for receiving context to theauthorized transaction, an attendees field for receiving a listing oneor more attendees associated with the authorized transaction, and aproject field for receiving relevant project codes associated with theauthorized transaction.

In certain implementations, certain portions of the configurable datamay be automatically generated and/or predicted. For example, if thevirtual transaction card is used during a calendar event (e.g., abusiness lunch) and/or at an expected location, user device 120 mayidentify individuals who accepted a calendar invite to populate anattendee list. In other instances, user device 120 may identifyproximate external devices (e.g., user devices of other individuals)through, for example, connections (e.g., Bluetooth), proximity sensors,and/or traffic sniffing, and populate an attendee list based onproximate attendees. In other cases, user device 120 may use geolocationdata (e.g., GPS data, IP addresses or networks, and/or merchantidentifiers) to determine which client and/or job corresponds to a givenpurchase. For example, if the user device 120 is located near a client'soffice, user device 120 may determine that client is the mostappropriate bill code. As another example, using continuous learningaround a user's behavior (e.g., previous tagging of previous vendors).

According to some embodiments, user device 120 may identify one or morepurchased items. For example, user device 120 may analyze the receiptdata to identify line items. In other cases, user device 120 may captureone or more images of purchased items, and identify (e.g., through imagematching) and list the purchased items. In some instances, user device120 may capture images of item barcodes and identify the items using(for example) a barcode reader. For example, user device 120 maytranslate the barcodes to numerical representations (e.g., productcodes) and match the product codes to specific purchased items.

User device 120 outputs 440 the purchase information in association withthe transaction. For example, in some cases, user device 120 maytransmit the purchase information to merchant device 140, and themerchant device may send the transaction server 130 the purchaseinformation (e.g., with the transaction authorization request or withthe payment request (posted transaction)). As another example, userdevice 120 may send the purchase information to the transactionmanagement server 110 associated with the pending transaction (e.g.,with a transaction ID). Transaction management server 110 may thenassociate output for transmission, to a transaction server, the receiptdata in association with the approved transaction.

As used in this application, the terms “component,” “module,” “system,”“server,” “processor,” “memory,” and the like are intended to includeone or more computer-related units, such as but not limited to hardware,firmware, a combination of hardware and software, software, or softwarein execution. For example, a component may be, but is not limited tobeing, a process running on a processor, an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a computing device and thecomputing device can be a component. One or more components can residewithin a process and/or thread of execution and a component may belocalized on one computer and/or distributed between two or morecomputers. In addition, these components can execute from variouscomputer readable media having various data structures stored thereon.The components may communicate by way of local and/or remote processessuch as in accordance with a signal having one or more data packets,such as data from one component interacting with another component in alocal system, distributed system, and/or across a network such as theInternet with other systems by way of the signal.

Certain embodiments and implementations of the disclosed technology aredescribed above with reference to block and flow diagrams of systems andmethods and/or computer program products according to exampleembodiments or implementations of the disclosed technology. It will beunderstood that one or more blocks of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, respectively, can be implemented by computer-executableprogram instructions Likewise, some blocks of the block diagrams andflow diagrams may not necessarily need to be performed in the orderpresented, may be repeated, or may not necessarily need to be performedat all, according to some embodiments or implementations of thedisclosed technology.

These computer-executable program instructions may be loaded onto ageneral-purpose computer, a special-purpose computer, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meansthat implement one or more functions specified in the flow diagram blockor blocks.

As an example, embodiments or implementations of the disclosedtechnology may provide for a computer program product, including acomputer-usable medium having a computer-readable program code orprogram instructions embodied therein, said computer-readable programcode adapted to be executed to implement one or more functions specifiedin the flow diagram block or blocks. Likewise, the computer programinstructions may be loaded onto a computer or other programmable dataprocessing apparatus to cause a series of operational elements or stepsto be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide elementsor steps for implementing the functions specified in the flow diagramblock or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specifiedfunctions, and program instruction means for performing the specifiedfunctions. It will also be understood that each block of the blockdiagrams and flow diagrams, and combinations of blocks in the blockdiagrams and flow diagrams, can be implemented by special-purpose,hardware-based computer systems that perform the specified functions,elements or steps, or combinations of special-purpose hardware andcomputer instructions.

Certain implementations of the disclosed technology are described abovewith reference to user devices may include mobile computing devices.Those skilled in the art recognize that there are several categories ofmobile devices, generally known as portable computing devices that canrun on batteries but are not usually classified as laptops. For example,mobile devices can include, but are not limited to portable computers,tablet PCs, internet tablets, PDAs, ultra-mobile PCs (UMPCs), wearabledevices, and smart phones. Additionally, implementations of thedisclosed technology can be utilized with internet of things (IoT)devices, smart televisions and media devices, appliances, automobiles,toys, and voice command devices, along with peripherals that interfacewith these devices.

In this description, numerous specific details have been set forth. Itis to be understood, however, that implementations of the disclosedtechnology may be practiced without these specific details. In otherinstances, well-known methods, structures and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription. References to “one embodiment,” “an embodiment,” “someembodiments,” “example embodiment,” “various embodiments,” “oneimplementation,” “an implementation,” “example implementation,” “variousimplementations,” “some implementations,” etc., indicate that theimplementation(s) of the disclosed technology so described may include aparticular feature, structure, or characteristic, but not everyimplementation necessarily includes the particular feature, structure,or characteristic. Further, repeated use of the phrase “in oneimplementation” does not necessarily refer to the same implementation,although it may.

Throughout the specification and the claims, the following terms take atleast the meanings explicitly associated herein, unless the contextclearly dictates otherwise. The term “connected” means that onefunction, feature, structure, or characteristic is directly joined to orin communication with another function, feature, structure, orcharacteristic. The term “coupled” means that one function, feature,structure, or characteristic is directly or indirectly joined to or incommunication with another function, feature, structure, orcharacteristic. The term “or” is intended to mean an inclusive “or.”Further, the terms “a,” “an,” and “the” are intended to mean one or moreunless specified otherwise or clear from the context to be directed to asingular form. By “comprising” or “containing” or “including” is meantthat at least the named element, or method step is present in article ormethod, but does not exclude the presence of other elements or methodsteps, even if the other such elements or method steps have the samefunction as what is named.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

While certain embodiments of this disclosure have been described inconnection with what is presently considered to be the most practicaland various embodiments, it is to be understood that this disclosure isnot to be limited to the disclosed embodiments, but on the contrary, isintended to cover various modifications and equivalent arrangementsincluded within the scope of the appended claims. Although specificterms are employed herein, they are used in a generic and descriptivesense only and not for purposes of limitation.

This written description uses examples to disclose certain embodimentsof the technology and also to enable any person skilled in the art topractice certain embodiments of this technology, including making andusing any apparatuses or systems and performing any incorporatedmethods. The patentable scope of certain embodiments of the technologyis defined in the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral language of the claims.

An embodiment of the present disclosure may be implemented according toat least the following:

Clause 1: A method including: receiving an indication of a transactionauthorization of a pending transaction, the transaction authorizationbeing requested using a financial account associated with a user;outputting for transmission, to a user device associated with the user,a request for purchase information corresponding to the pendingtransaction; receiving, from the user device, receipt image datacorresponding to a receipt related the pending transaction; storing dataindicative of the receipt in correspondence with the pendingtransaction; determining, based on analyzing a plurality of postedtransactions of the financial account, a first posted transactioncorresponding to the pending transaction; and storing the dataindicative of the receipt in correspondence with the first postedtransaction.

Clause 2: The method of clause 1 further including: receiving, with thereceipt image data, transaction classification information; storing thetransaction classification information in correspondence with thepending transaction; and storing the transaction classificationinformation in correspondence with the first posted transaction.

Clause 3: The method of clauses 1 or 2 further including: analyzing thereceipt image data using optical character recognition; and extractingreceipt information from the analyzed receipt image data as the dataindicative of the receipt image.

Clause 4: The method of any of clauses 1-3, wherein the pendingtransaction has a first transaction value, and the first postedtransaction has a second, different transaction value.

Clause 5: The method of clause 4, wherein determining the first postedtransaction includes: analyzing the receipt image data to identify oneor more post-authorization line-items, adjusting the first transactionvalue in accordance with the identified one or more post-authorizationline items, and determining the first posted transaction based at leastin part on the adjusted first transaction value.

Clause 6: The method of any of clauses 1-5, wherein the request forpurchase information corresponding to the pending transaction isconfigured to trigger a persistent request for the receipt image data.

Clause 7: A user device including: at least one processor; and at leastone memory having stored thereon computer program code that, whenexecuted by the at least one processor, controls the user device to:activate, on the user device, a virtual wallet application, the virtualwallet application including one or more virtual transaction cards;responsive to a first virtual transaction card of the one or morevirtual transaction cards being utilized in an approved transaction,output for display, on the user device, a prompt to provide purchaseinformation; receive receipt data corresponding to a receipt related theapproved transaction; and output for transmission, to a transactionserver, the receipt data in association with the approved transaction.

Clause 8: The user device of clause 7 further including a camera,wherein receiving the receipt data corresponding to the receiptincludes: activating, on the user device, a camera applicationcorresponding to the camera; and capturing, using the camera and thecamera application, an image of the receipt.

Clause 9: The user device of clause 8, wherein the computer programcode, when executed by the at least one processor, further controls theuser device to verify the image corresponds to the receipt.

Clause 10: The user device of clause 9, wherein verifying the imagecorresponds to the receipt includes: analyzing the image using one ormore optical-character recognition algorithms; and comparing theanalyzed image with transaction information of the approved transaction.

Clause 11: The user device of any clauses 7-10, wherein receiving thereceipt data corresponding to the receipt includes: activating, on theuser device, an email application; identifying, within the emailapplication, a receipt email from among a plurality of emails; andextracting receipt information from the identified receipt email.

Clause 12: The user device of clause 11, wherein identifying the receiptemail includes identifying the receipt email based on at least one fromamong respective delivery dates of the plurality of emails, respectivesender addresses of the plurality of emails, and text-analysis of one ormore of the plurality of emails.

Clause 13: The user device of clauses 11 or 12, wherein extracting thereceipt information includes capturing a screenshot of the identifiedreceipt email.

Clause 14: The user device of clauses 11-13, wherein extracting thereceipt information includes forwarding the identified receipt email toan address associated with the transaction server.

Clause 15: The user device of clause 14, wherein forwarding theidentified receipt email includes: receiving an indication of a userinput of additional transaction information, the additional transactioninformation including one or more of notes, a list of attendees, andproject codes; and forwarding the additional transaction informationtogether with the identified receipt email to the address associatedwith the transaction server.

Clause 16: The user device of clauses 7-15, wherein the computer programcode, when executed by the at least one processor, further controls theuser device to: execute, on the user device, a receipt capturingapplication; receive the receipt data within the receipt capturingapplication; and provide, within the receipt capturing application, atleast one from among: a notes field for receiving context to anauthorized transaction, an attendees field for receiving a listing oneor more attendees associated with the authorized transaction, and aproject field for receiving relevant project codes associated with theauthorized transaction.

Clause 17: The user device of clause 16, wherein the computer programcode, when executed by the at least one processor, further controls theuser device to automatically populate the attendees field based on alist of attendees of an event associated with the authorizedtransaction.

Clause 18: The user device of clauses 16 or 17 further including acamera, wherein the computer program code, when executed by the at leastone processor, further controls the user device to: activate, on theuser device, a camera application corresponding to the camera; capture,using the camera and the camera application, one or more images of oneor more purchased items associated with the authorized transaction;identify, based on the one or more images, one or more item identitiescorresponding one or more purchased items; and output for transmission,to the transaction server, data indicative of a list of the one or moreitems in association with the approved transaction.

Clause 19: The user device of clause 18, wherein the camera applicationincludes a barcode reader, and identifying the one or more itemsincludes identifying, within the one or more images, one or morebarcodes corresponding to the one or more items; transforming the one ormore barcodes into one or more numerical representations; and matchingthe one or more numerical representations to identities of the one ormore items.

Clause 20: A system including: at least one processor; and at least onememory having stored thereon computer program code that, when executedby the at least one processor, controls the system to: receive, from auser device, an indication of a pending transaction conducted using avirtual transaction card associated with a financial account maintainedby a financial institution, the virtual transaction card beinginstantiated on the user device; outputting for transmission, to theuser device, a request for purchase information corresponding to thepending transaction; receiving, from the user device, receipt image datacorresponding to a receipt related the pending transaction; storing dataindicative of the receipt in correspondence with the pendingtransaction; determining, based on analyzing a plurality of postedtransactions of the financial account, a first posted transactioncorresponding to the pending transaction; and storing the dataindicative of the receipt in correspondence with the first postedtransaction.

Clause 21: A non-transitory computer readable medium having storedthereon instructions for executing a method according to any of clauses1-6.

EXAMPLE USE CASES

The following example use cases describe examples of a use of systemsand methods for appending data to pending transactions and attaching tocorresponding posted transaction. These examples use cases are intendedsolely for explanatory purposes and not for limitation. In one case, auser wishes to easily annotate transactions. Accordingly, the userregisters his credit card(s) and user device(s) with a transactionmanager (e.g., transaction management server 110). The transactionmanager may link to the credit card account(s) at a financialinstitution (e.g., transaction server 130). When a transactionauthorization request is approved for the credit card account, theaccount has a pending transaction. The financial institution alerts thetransaction manager of the pending transaction. The transaction managerthen prompts the user device(s) for purchase information (e.g.,receipts, attendees, internal codes, itemized purchase list). In otherwords, the transaction becoming pending in the credit card accounttriggers the request for purchase information. The transaction managerreceives the purchase information and associates it with the pendingtransaction. Later, financial transfers may occur, and transactions willpost to the credit card account. The financial institution sends theposted transactions to the transaction manager. The transaction manageranalyzes the posted transactions to identify one that corresponds to thepending transaction. Once identified, the transaction manager associatesthe purchase information with the posted transaction. The transactionmanager may generate expense reports associated with the transaction(i.e., based on the purchase information) and submit the same to theuser.

In another case, a user wishes to easily annotate transactions.Accordingly, the user configures her personal device (e.g., user device120) such that, when a virtual transaction card is used, it triggers arequest for purchase information. For instance, the personal device mayinclude virtual wallet with a virtual transaction card. When the virtualtransaction card is used (e.g., when it pars with a payment terminalsuch as merchant device 140), the personal device outputs a prompt forthe purchase information. The user can input the purchase informationdirectly into the device (e.g., by capturing a picture of a receipt orthrough fields in an expense management application). In some cases, thepersonal device can automatically gather the purchase information, suchas by accessing a user's email account to retrieve a receipt email andby identifying attendees (e.g., through calendar requests) or purchasecodes (e.g., based on a location of the personal device). The userdevice may share the purchase information with a server (e.g.,transaction server 130 and/or transaction management server 110), whichcan then attach the information to a pending transaction (and ultimatelya settled transaction).

1-6. (canceled)
 7. A user device comprising: at least one processor; andat least one memory having stored thereon computer program code that,when executed by the at least one processor, controls the user deviceto: activate, on the user device, a virtual wallet application, thevirtual wallet application including one or more virtual transactioncards; responsive to a first virtual transaction card of the one or morevirtual transaction cards being utilized in an approved transaction viathe virtual wallet application activated on the user device, output fordisplay, on the user device, a prompt to provide receipt data of areceipt for the approved transaction; receive, by the user device, thereceipt data corresponding to the receipt for the approved transaction;and output for transmission, from the user device and to a transactionserver of a financial institution processing the approved transaction,the receipt data to be stored in association with the approvedtransaction by the financial institution.
 8. The user device of claim 7further comprising a camera, wherein receiving the receipt datacorresponding to the receipt comprises: activating, on the user device,a camera application corresponding to the camera; and capturing, usingthe camera and the camera application, an image of the receipt.
 9. Theuser device of claim 8, wherein the computer program code, when executedby the at least one processor, further controls the user device toverify that the image captured using the camera corresponds to thereceipt for the approved transaction.
 10. The user device of claim 9,wherein verifying that the image corresponds to the receipt comprises:analyzing the image captured using the camera using one or moreoptical-character recognition algorithms; and comparing receipt dataextracted from the analyzed image with transaction information of theapproved transaction.
 11. The user device of claim 7, wherein receivingthe receipt data corresponding to the receipt comprises: activating, onthe user device, an email application; automatically identifying, withinthe email application, a receipt email from among a plurality of emailsstored by the email application; and automatically extracting, by theuser device, the receipt data from the identified receipt email.
 12. Theuser device of claim 11, wherein identifying the receipt email comprisesidentifying the receipt email based on at least one from amongrespective delivery times of the plurality of emails, respective senderaddresses of the plurality of emails, and text-analysis of one or moreof the plurality of emails.
 13. The user device of claim 11, whereinextracting the receipt data comprises capturing, by the user device, ascreenshot of the identified receipt email.
 14. The user device of claim11, wherein extracting the receipt data comprises automaticallyforwarding, by the user device, a copy of the identified receipt emailto an address associated with the transaction server.
 15. The userdevice of claim 14, wherein forwarding the identified receipt emailcomprises: receiving an indication of a user input of additionaltransaction information, the additional transaction informationcomprising one or more of notes, a list of attendees, and project codes;and forwarding the additional transaction information together with theidentified receipt email to the address associated with the transactionserver.
 16. The user device of claim 7, wherein the computer programcode, when executed by the at least one processor, further controls theuser device to: execute, on the user device, a receipt capturingapplication; receive the receipt data within the receipt capturingapplication, the receipt data being input by a user of the user deviceinto the receipt capturing application; and provide, within the receiptcapturing application, at least one from among: a notes field forreceiving context to an authorized transaction, an attendees field forreceiving a listing one or more attendees associated with the authorizedtransaction, and a project field for receiving relevant project codesassociated with the authorized transaction.
 17. The user device of claim16, wherein the computer program code, when executed by the at least oneprocessor, further controls the user device to automatically populatethe attendees field based on a list of attendees of an event associatedwith the authorized transaction.
 18. The user device of claim 16 furthercomprising a camera, wherein the computer program code, when executed bythe at least one processor, further controls the user device to:activate, on the user device, a camera application corresponding to thecamera; capture, using the camera and the camera application, one ormore images of a plurality of purchased items purchased by theauthorized transaction; automatically identify, based on an analysis ofthe one or more images, a plurality of item identities corresponding tothe plurality of purchased items; and output for transmission, to thetransaction server, data indicative of a list of the plurality of itemidentities in association with the approved transaction.
 19. The userdevice of claim 18, wherein the camera application comprises a barcodereader, and identifying the one or more item identities comprises:identifying, within the one or more images, one or more barcodescorresponding to the one or more purchased items; transforming the oneor more barcodes into one or more numerical representations; andmatching the one or more numerical representations to identities of theone or more purchased items.
 20. (canceled)
 21. A method comprising:activating, on a user device, a virtual wallet application, the virtualwallet application including one or more virtual transaction cards;responsive to a first virtual transaction card of the one or morevirtual transaction cards being utilized in an approved transaction viathe virtual wallet activated on the user device, outputting for display,on the user device, a prompt to provide receipt data of a receipt forthe approved transaction; receiving, by the user device, the receiptdata corresponding to the receipt for the approved transaction; andoutputting for transmission, from the user device and to a transactionserver of a financial institution processing the approved transaction,the receipt data to be stored in association with the approvedtransaction.
 22. The method of claim 21, wherein receiving the receiptdata corresponding to the receipt comprises: activating, on the userdevice, a camera application corresponding to a camera of the userdevice; and capturing, using the camera and the camera application, animage of the receipt.
 23. The method of claim 22 further comprisingverifying that the image captured using the camera corresponds to thereceipt for the approved transaction.
 24. The method of claim 23,wherein verifying that the image corresponds to the receipt for theapproved transaction comprises: analyzing the image captured using thecamera using one or more optical-character recognition algorithms; andcomparing receipt data extracted from the analyzed image withtransaction information of the approved transaction.
 25. The method ofclaim 21, wherein receiving the receipt data corresponding to thereceipt comprises: activating, on the user device, an email application;automatically identifying, within the email application, a receipt emailfrom among a plurality of emails stored by the email application; andautomatically extracting the receipt data from the identified receiptemail.
 26. The method of claim 25, wherein identifying the receipt emailcomprises identifying the receipt email based on at least one from amongrespective delivery times of the plurality of emails, respective senderaddresses of the plurality of emails, and text-analysis of one or moreof the plurality of emails.
 27. A non-transitory computer readablemedium having stored thereon computer program code that, when executedby one or more processors of a user device, controls the user device toperform a method comprising: activating, on the user device, a virtualwallet application, the virtual wallet application including one or morevirtual transaction cards; responsive to a first virtual transactioncard of the one or more virtual transaction cards being utilized in anapproved transaction via the virtual wallet application activated on theuser device, outputting for display, on the user device, a prompt toprovide receipt data of a receipt for the approved transaction;receiving, by the user device the receipt data corresponding to thereceipt for the approved transaction; and outputting for transmission,from the user device and to a transaction server of a financialinstitution processing the approved transaction, the receipt data to bestored in association with the approved transaction.